docs: align 3.x upgrade guide with the shipped 1.x env_migrate task#45
Merged
turegjorup merged 1 commit intoJun 23, 2026
Merged
Conversation
PR #43 (merged) reconciled the 1.x prep tooling with the already-merged `task env_migrate` (#40): the 1.x converter wrapper is `env_migrate` and it writes `.env.symfony.migrated`, not the `task upgrade_prep`/`env.3x` this branch's guide assumed. Retarget the 3.x side to that reality. - env:migrate (3.x): take the `.env.symfony.migrated` produced on 1.x by `task env_migrate` (carried across the branch switch, gitignored on both) and split its trailing infrastructure advisory in place, instead of looking for `env.3x`. Fall back to the sed conversion of `.env.docker.local` when it's absent. Idempotent on re-run. - UPGRADE.md, README, CHANGELOG: replace every `task upgrade_prep` / `env.3x` reference with `task env_migrate` / `.env.symfony.migrated`. - Fix a stale "UPGRADE.md step 6" pointer in env:migrate to "step 4" (the MariaDB step's number after the #44 restructure). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #44. When #43 merged it reconciled the 1.x prep tooling with the already-merged
task env_migrate(#40): on the 1.x branch the converter wrapper istask env_migrateand it writes.env.symfony.migrated— not thetask upgrade_prep/env.3xthat #44's guide andenv:migratetask assumed. This retargets the 3.x side so the cross-branch flow actually works end to end.Without this, operators following
UPGRADE.mdonrelease/3.0.0would run atask upgrade_prepthat doesn't exist and look for anenv.3xthat's never produced.Changes
Taskfile.yml(env:migrate): consume the.env.symfony.migratedproduced on 1.x bytask env_migrate(it survives the branch switch — gitignored on both branches) and split its trailing infrastructure advisory in place (input and output share the name), instead of readingenv.3x. Falls back to the sed conversion of.env.docker.localwhen absent; idempotent on re-run.UPGRADE.md/README.md/CHANGELOG.md: replace everytask upgrade_prep/env.3xreference withtask env_migrate/.env.symfony.migrated.UPGRADE.md step 6pointer inenv:migrate→step 4(the MariaDB step's number after the docs: restructure 1.x → 3.x upgrade around the 2.8 config converter #44 restructure).Test Plan
task env:migrateexercised three ways: a converter-shaped.env.symfony.migrated(advisory split in place into.env.symfony.infra-advisory, clean app env retained); a second run (idempotent — no advisory left, file unchanged); and no migrated file present (sed fallback on.env.docker.local,APP_strip).task --listparses;scripts/check-tasks-readme.shpasses.markdownlint(repo image + config) clean onUPGRADE.md,README.md,CHANGELOG.md.grepconfirms noenv.3x/upgrade_prepreferences remain on the branch.🤖 Generated with Claude Code